Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pinned all dependencies #895

Closed
wants to merge 1 commit into from
Closed

Pinned all dependencies #895

wants to merge 1 commit into from

Conversation

stephenplusplus
Copy link
Contributor

👋 Hello!

We’re all trying to keep our software up to date, yet stable at the same time.

This is the first in a series of automatic PRs to help you achieve this goal. It pins all of the dependencies in your package.json, so you have complete control over the exact state of your software.

From now on you’ll receive PRs whenever one of your dependencies updates – in real time. This way you get all the benefits of up-to-date dependencies, while having them pinned at the same time. This means:

  • No more surprises because some of your dependencies didn’t follow SemVer. Your software is always in a state you know about, regardless of when someone does $ npm install.
  • If you have continuous integration set up for this repo, it’ll run automatically. Ideally, it will pass and you'll stay up to date with the press of a button. If the updated dependency does break your software, it won’t affect your users, because their dependencies are still pinned to the working state.
  • You can immediately identify which dependency updates break your software, because each one is tested in isolation. You’ll also have a branch ready to work on, so adapting to new APIs is way faster.

Merge this PR and you’ll have up-to-date software without the headaches ✨


This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for the commit author(s). If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.

@googlebot googlebot added the cla: no This human has *not* signed the Contributor License Agreement. label Sep 25, 2015
@stephenplusplus
Copy link
Contributor Author

@jgeewax this is a robot that's going to take care of our dependencies for us (like it said). Do robots need to sign the CLA?

@stephenplusplus
Copy link
Contributor Author

On second thought, this might be a bad idea. npm3 will have deduplication, which this would disable. We also might be getting PRs all day every day since we have so many.

@stephenplusplus stephenplusplus deleted the greenkeeper-pin branch October 8, 2015 13:29
sofisl pushed a commit that referenced this pull request Nov 11, 2022
… time zone on conversation profile (#895)

* feat: added support to configure security settings, language code and time zone on conversation profile

PiperOrigin-RevId: 407663596

Source-Link: googleapis/googleapis@f9acb37

Source-Link: googleapis/googleapis-gen@aa54a75
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiYWE1NGE3NTcwNjhmMDA1YWIyMTA2NGZiMjA4YTVlYzU5N2U0OWE5YSJ9

* 🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

* 🦉 Updates from OwlBot

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this pull request Jan 17, 2023
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: no This human has *not* signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants